Skip to content

Per-node UBO population and per-frame cam state access#676

Open
skalarproduktraum wants to merge 2 commits into
mainfrom
feature/per-frame-cam-state
Open

Per-node UBO population and per-frame cam state access#676
skalarproduktraum wants to merge 2 commits into
mainfrom
feature/per-frame-cam-state

Conversation

@skalarproduktraum
Copy link
Copy Markdown
Member

@skalarproduktraum skalarproduktraum commented Feb 1, 2024

This PR introduces:

  • the PopulatesUBO interface, which enables node to define their own serialisation procedure, aka, how to translate a node's information into something accessible to shaders that goes beyond ShaderProperties
  • access to a given frame's camera state in the Vulkan renderer's render() and submitFrame() function.

return true
}

override var nodeType = "Node"
Copy link
Copy Markdown
Contributor

@smlpt smlpt Feb 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this cause any trouble in other parts of scenery that rely on this node type?
Or rather: will removing the property nodeType altogether result in any unexpected behavior in other parts of scenery?

}
}

var stereoEnabled = false
Copy link
Copy Markdown
Contributor

@smlpt smlpt Feb 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this false if it is a stereo camera?

Copy link
Copy Markdown
Contributor

@smlpt smlpt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but maybe add a short documentation to the populate UBO classes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants